This option adds unique station address entries to the permanent database. These entries are copied into the filtering database as permanent entries when the bridge is restarted.
The Destination Address is the MAC address of the desired entry. It can be an individual address, multicast address, or broadcast address. Permanent database entries are not destroyed by the power off/on process and are immune to the aging settings. Permanent entries cannot be replaced by dynamic entries.
These entries represent addresses that you may want to filter in various ways. To add a destination address, type in the MAC address, which is a 12-byte hexadecimal number.
Valid Values: X'0000 0000 0000' to X'FFFF FFFF FFFF'
Default Value: none
This option lets you set destination address filtering for that entry. Answering "Yes" causes filtering of any frame that contains this address as a destination address no matter which port it came from.
This option allows for port-specific address filtering. When SAF is applied ("Yes" is entered), frames received with source addresses that match address entries in the filtering database that have source address filtering enabled will be discarded. This mechanism allows a network manager to isolate an end station by prohibiting its traffic from being bridged.
Select the Submit button.
You can configure the router to map received packets based on their protocol type.
Some protocols use group addresses for Ethernet that do not correspond to the equivalent functional addresses used in token-ring.
This option adds a specific functional address to group address mapping for the Destination Service Access Point (DSAP) protocol.
Address parameters enable you to specify certain protocols. Within these protocols (identified by Ethernet type, SNAP, or SAP), you must specify certain group addresses. These group addresses are mapped to certain functional addresses that you specify. The purpose of the parameters is to enable the bridge to forward information for certain group addresses to specified functional addresses and do the reverse. The parameters enable group address traffic to traverse both transparent (TB) and source routing bridge (SRB) LAN segments in a source routing transparent (SRT) or adaptive source routing transparent (ASRT) bridge (that is, SR-TB Conversion).
Enter the following information:
This parameter specifies the Destination Service Access Point (DSAP) protocol type (in hexadecimal).
Valid Values: X'1' to X'FE'
Common values are:
Protocol - SAP (hexadecimal value)
Default Value: 1
This parameter specifies the 6-byte (12-digit hexadecimal) group/multicast address.
Valid Values: X'0000 0000 0000' to X'FFFF FFFF FFFF'
Default Value: none
This parameter specifies the locally-administered group address in non-canonical format. These are most commonly used in token-ring networks.
Valid Values: X'0000 0000 0000' to X'FFFF FFFF FFFF'
Default Value: none
Select the Submit button.
You can configure the router to map received packets based on their protocol type.
Some protocols use group addresses for Ethernet that do not correspond to the equivalent functional addresses used in token-ring.
This option adds a specific functional address to group address mapping for Ethernet.
The address parameters enable you to specify certain protocols. Within these protocols (identified by Ethernet type, SNAP, or SAP), you must specify certain group addresses. These group addresses are mapped to certain functional addresses that you specify. The purpose of the parameters is to enable the bridge to forward information for certain group addresses to specified functional addresses and do the reverse. The parameters enable group address traffic to traverse both transparent (TB) and source routing bridge (SRB) LAN segments in a source routing transparent (SRT) or adaptive source routing transparent (ASRT) bridge (that is, SR-TB Conversion).
The address mapping is converted only on destination addresses crossing Token Ring to Ethernet or vice versa.
Note: For every Ether-type mapped value, the corresponding SNAP-type value should be added. This is necessary for bidirectional mapping.
Enter the following information:
This parameter specifies the Ethernet protocol type (in hexadecimal).
Valid Values: X'5DD' to X'FFFF'
Protocol - Ethernet type (hex value)
Default Value: 1
This parameter specifies the 6-byte (12-digit hexadecimal) group/multicast address.
Valid Values: X'0000 0000 0000' to X'FFFF FFFF FFFF'
Default Value: none
This parameter specifies the locally-administered group address in non-canonical format. These are most commonly used in token-ring networks.
Valid Values: X'0000 0000 0000' to X'FFFF FFFF FFFF'
Default Value: none
Select the Submit button.
You can configure the router to map received packets based on their protocol type.
This option adds a specific functional address to group address mapping for SubNetwork Access Protocol (SNAP).
This option adds a specific functional address to group address mapping for Ethernet.
The address parameters enable you to specify certain protocols. Within these protocols (identified by Ethernet type, SNAP, or SAP), you must specify certain group addresses. These group addresses are mapped to certain functional addresses that you specify. The purpose of the parameters is to enable the bridge to forward information for certain group addresses to specified functional addresses and do the reverse. The parameters enable group address traffic to traverse both transparent (TB) and source routing bridge (SRB) LAN segments in a source routing transparent (SRT) or adaptive source routing transparent (ASRT) bridge (that is, SR-TB Conversion).
The address mapping is converted only on destination addresses crossing Token Ring to Ethernet or vice versa.
Note: For every Ether-type mapped value, the corresponding SNAP-type value should be added. This is necessary for bidirectional mapping.
Enter the following information:
This parameter specifies the SNAP protocol type (in hexadecimal).
In LANs, a 5-byte protocol discriminator that identifies the non-IEEE standard protocol family to which a packet belongs. The SNAP value is used to differentiate between protocols that use X'AA' as their service access point (SAP) value.
The first 6 digits are the Organizationally Unique Identifier (OUI) and the last 2 digits are the Ethernet type value.
Valid Values: X'00 0000 0000' to X'FF FFFF FFFF'
Common values are:
Default Value: 00 0000 0800
This parameter specifies the 6-byte (12-digit hexadecimal) group/multicast address.
Valid Values: X'0000 0000 0000' to X'FFFF FFFF FFFF'
Default Value: none
This parameter specifies the locally-administered group address in non-canonical format. These are most commonly used in token-ring networks.
Valid Values: X'0000 0000 0000' to X'FFFF FFFF FFFF'
Default Value: none
Select the Submit button.
By default, the ASRT protocol has one bridging port, port 1. This port is associated with interface 0, the LAN interface. You must add other ports on which you want to perform bridging.
By default, an added port bridges packets using transparent bridging.
This option adds a LAN port to the bridging configuration. This associates a port number with the interface number and enables that port's participation in transparent bridging.
This parameter specifies the interface you are using for this port.
Port numbers are assigned to each interface as the previous interface number plus 1. For example, interface 0, would be assigned the port number of 1.
This parameter defines the circuit number of the circuit being configured. The value must be in the range supplied by the network provider.
For statically configured destination protocol address mappings, this parameter defines the circuit that the protocol is to run over.
Valid Values: 16 to 1007
Default Value: none
Valid Values: 0 - 255
Default Value: 0
Valid Values: 0 - 65535
Default Value: 0
Valid Values: Any valid 40-hexadecimal digit ATM address
Default Value: None
Valid Values: Any valid selector in the range of X'00' - X'FF"
Default Value: None
Select the Submit button.
This option allows the bridge to be configured so that it can selectively filter destination service access point (DSAP) packets based on their protocol type. Filters can be applied to all ports or only to selected ports.
Selecting this parameter means that DSAP frames are discarded exclusively without applying bridge logic. ARP packets for this protocol type will also be discarded. The protocol filter is applied only on the received packets.
This parameter specifies the Destination Service Access Point (DSAP) protocol type (in hexadecimal).
Valid Values: X'1' to X'FE'
Common values are:
Protocol - SAP (hexadecimal value)
Default Value: 1
Select the Submit button.
This option allows the bridge to be configured so that it can selectively filter Ethernet packets based on their protocol type. Filters can be applied to all ports or only selected ports.
Selecting this parameter means that Ethernet frames are discarded exclusively without applying bridge logic. ARP packets for this protocol type will also be discarded. The protocol filter is applied only on the received packets.
Valid Values: X'5DD' to X'FFFF'
Protocol - Ethernet type (hex value)
Default Value: none
Select the Submit button.
This option allows the bridge to be configured so that it can selectively filter SNAP packets based on their protocol type. Filters can be applied to all ports or only selected ports.
This option means that SNAP frames are discarded exclusively without applying bridge logic. ARP packets for this protocol type will also be discarded. The protocol filter is applied only on the received packets.
Valid Values: X'00 0000 0000' to X'FF FFFF FFFF'
Common values are:
Default Value: 00 0000 0800
Select the Submit button.
The tunnel bridge allows source route bridge domains or transparent bridge domains to communicate across an IP network.
To allow IBM LAN and terminal traffic to merge with non-IBM traffic (that is, Novell) across a single backbone, the Source Routing Bridge Tunnel and SDLC (Synchronous Data Link Control) Relay features of the bridging router software encapsulate IBM traffic within industry-standard TCP/IP packets. The bridging router then routes these packets using an IP path or tunnel through large IP internetworks. The benefit is increased functionality and network utilization as well as higher network availability and increased ease of use.
End-stations see the IP path (the tunnel) as a single hop, regardless of the network complexity. This helps overcome the usual 7-hop distance limit encountered in source routing configurations. It also lets you connect source-routing end-stations across non-source-routing media, such as Ethernet networks.
The bridging tunnel also overcomes several limitations of regular source routing including:
With the bridge tunnel feature enabled, the software encapsulates packets in TCP/IP packets. To the router, the packet looks like a TCP/IP packet. Once a frame is encapsulated in an IP envelope, the IP forwarder is responsible for selecting the appropriate network interface based on the destination IP address. This packet can be routed dynamically through large internetworks without degradation or network size restrictions. End-stations see this path, or tunnel, as a single hop regardless of the complexity of the internetwork.
The tunnel is transparent to the end stations. The bridging routers participating in tunneling treat the IP internet as one of the bridge segments. When the packet reaches the destination interface, the TCP/IP headers are automatically removed and the inner packet proceeds as a standard source routing packet.
Add Tunnel creates the user-defined IP tunnel to a bridge port. This tunnel is counted as only one hop between the bridges no matter how complex the path through the IP internet. To use the tunnel feature, the IP forwarder must be enabled.
Only one tunnel can be added. It is required that for the Port Number, you use one that is not used for any other LAN port. Internally, the interface number 255 is ascribed to mark that interface as connected as a "virtual" interface.
Transparent bridging is enabled on this port by default. Source routing can be enabled, however, by using the Enable Source-Routing option.
Enter the port number. This port number must be a unique port number that is not being used by the bridge.
Select the Submit button.
This option changes bridge numbers in the bridging configuration.
Enter the new bridge number.
Select the Submit button.
If you have more than one port customized, you will be prompted for the internal virtual segment number. This is used to simulate a virtual segment and will add a hop in the routing information field (RIF).
This option changes segment numbers in the bridging configuration.
Select the Submit button.
Deletes an address entry from the permanent database. Enter the MAC address value (in 12-digit hexadecimal format) of the entry to be deleted and select Submit.
Reserved multicast addresses cannot be deleted. If you attempt to delete an address entry that does not exist, you will receive the message
Record matching that address not found
Enter the MAC address to be deleted.
Valid Values: X'0000 0000 0000' to X'FFFF FFFF FFFF'
Default Value: none
Select the Submit button.
You can configure the router to map received packets based on their protocol type.
This option deletes specific address mapping for DSAP.
Enter the following information:
This parameter specifies the Destination Service Access Point (DSAP) protocol type (in hexadecimal).
Valid Values: X'1' to X'FE'
Common values are:
Protocol - SAP (hexadecimal value)
Default Value: 1
This parameter specifies the 6-byte (12-digit hexadecimal) group/multicast address.
Valid Values: X'0000 0000 0000' to X'FFFF FFFF FFFF'
Default Value: none
Select the Submit button.